Are you able to just add these constraints where necessary? This would avoid making a breaking change

Are you able to just add these constraints where necessary? This would avoid making a breaking change

Hmm, but the Datum is basically Scalar. It is a struct not a trait and it is not implemented with Send. Can I add Send as constraint for it outside this crate? I think it doesn't work if I add it like Datum + Send?

You can add constraints for marker traits at point of usage

Sorry, I still don't know how can I add Send as a constraint to Scalar outside this crate. 🤔

I can let the function return Datum + Send so Send is a constraint of the returned type. But Scalar doesn't implement Send, how can I make it implement Send outside this crate?

I'm confused, Scalar is just a wrapper around a T: Array that implements Datum, whether or not Datum has additional constraints or not has no bearing on whether Scalar is Send?

Perhaps you could provide a small code reproducer?

I'm confused, Scalar is just a wrapper around a T: Array that implements Datum, whether or not Datum has additional constraints or not has no bearing on whether Scalar is Send?

Perhaps you could provide a small code reproducer?

Hmm, do you mean to return Array (a Send) instead of Scalar?

Because Scalar is not a Send, although it is simply a wrapper of Array, I guess it cannot be used as Send automatically? I think it cannot be but let me try it first. Thanks.

Send is an auto-trait that will be automatically derived if the contents of the type are themselves Send. The same is true for Sync.

I just tried it. Looks like it works.

Because Scalar is not a Send, although it is simply a wrapper of Array, I guess it cannot be used as Send automatically? I think it cannot be but let me try it first. Thanks.

Interesting. So even Scalar is not a Send, if Rust compiler knows it is a wrapper of Array, it will be automatically a Send?

fn get_arrow_datum(datum: &Datum) -> Result<Box<dyn ArrowDatum + Send>> {
    match datum.literal() {
        PrimitiveLiteral::Boolean(value) => Ok(Box::new(BooleanArray::new_scalar(*value))),
        PrimitiveLiteral::Int(value) => Ok(Box::new(Int32Array::new_scalar(*value))),
        PrimitiveLiteral::Long(value) => Ok(Box::new(Int64Array::new_scalar(*value))),
        PrimitiveLiteral::Float(value) => Ok(Box::new(Float32Array::new_scalar(value.as_f32()))),
        PrimitiveLiteral::Double(value) => Ok(Box::new(Float64Array::new_scalar(value.as_f64()))),
        l => Err(Error::new(
            ErrorKind::DataInvalid,
            format!("Unsupported literal type: {:?}", l),
        )),
    }
}

fn some_func(...) {
    let literal = get_arrow_datum(&literal)?;

    ....
    move |batch| {
        let left = batch.column(term_index);
         lt(left, literal.as_ref())
    },
    ....
}

Send is an auto-trait that will be automatically derived if the contents of the type are themselves Send. The same is true for Sync.

Ah, got it. I thought it needs to explicitly implement it. Learn it. Thank you @tustvold !